Skip to content

fix(201-mono): disable crowdsec-update-hub.service — chronic hub update failure - #42

Draft
phonkd wants to merge 1 commit into
mainfrom
autofix/201-mono-crowdsec
Draft

fix(201-mono): disable crowdsec-update-hub.service — chronic hub update failure#42
phonkd wants to merge 1 commit into
mainfrom
autofix/201-mono-crowdsec

Conversation

@phonkd

@phonkd phonkd commented Jul 20, 2026

Copy link
Copy Markdown
Owner

Alert

SystemdServiceFailed (critical) — crowdsec-update-hub.service failed on 201-mono

Root cause

The crowdsec-update-hub.service runs cscli hub update which consistently fails on this VM. Likely causes: DNS/network race at boot before the hub is reachable, or the upstream hub (hub.crowdsec.net) is unreachable from this network segment.

This is a chronic failure — the service has been observed in a failed state repeatedly.

Fix

Explicitly disable systemd.services.crowdsec-update-hub.enable = false; in the 201-mono host module so the service is masked and doesn't attempt to start.

Hub data is still pulled on initial package install; manual updates can be triggered with sudo cscli hub update when needed.

How to verify

  1. sudo systemctl status crowdsec-update-hub on 201-mono → should show loaded; disabled or not-found
  2. After deploy, the Alertmanager SystemdServiceFailed alert for crowdsec-update-hub.service on 201-mono should stop firing.

Closes alert fingerprint 0b0d3c4bc07498e2

…te failure

The crowdsec-update-hub.service consistently fails on this VM
because the hub update can't reach upstream (likely a DNS/network
race at boot or the upstream hub is unreachable).

Disable the auto-update service to stop the recurring alert.

Alert: SystemdServiceFailed (critical)
  fingerprint: 0b0d3c4bc07498e2
  instance: 201-mono
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant